Release 3.55.5-9.4 - #28
Merged
Merged
Conversation
gduperrey
reviewed
Aug 24, 2026
gduperrey
left a comment
gduperrey
left a comment
Member
There was a problem hiding this comment.
Hello,
"fast track." <-- That isn't a milestone. In this case, it would be "next," alongside sm and xapi.
Regarding the explanation for users, could we have a few more details? "Fix qcow2 live coalesce with cbt activated."
- Fix commit command with cbt enabled. Signed-off-by: Anthoine Bourgeois <anthoine.bourgeois@vates.tech>
AnthoineB
force-pushed
the
abs-fix-commit-cbt
branch
from
August 24, 2026 16:12
5115f9b to
28a547a
Compare
gduperrey
approved these changes
Aug 25, 2026
gduperrey
left a comment
gduperrey
left a comment
Member
There was a problem hiding this comment.
Ok for me.
Regarding the target, you can check the "We already defined a release target with the release team" box in the template, since we're agreed on "next" :)
Nambrok
approved these changes
Aug 25, 2026
Contributor
Author
|
Koji build (v8.3-incoming): https://koji.xcp-ng.org/taskinfo?taskID=111699 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Main information
Work Item Reference
XCPNG-3669
Context & Motivation
This change fix the broken commit command with cbt activated.
Release Target
8.3-next
Release Notes and Documentation
Explain the change to users
Having QCOW2 with CBT enabled can lead to tapdisk opening the cbtlog disk as a first of the chain instead of qcow2 image, meaning that the commit related operations will return a ENOTSUPP.
The issue will escalate with the leaf-coalesce systematically failing and thus doing un-coalesceable VDIs and bloating the SRs.
This release will fix this issue by skipping the cbtlog image and select the right qcow2 image to coalesce.
Attention points
N/A
Documentation update needed
This not a new feature.
PR links: N/A.
Testing and regression avoidance
What tests have you performed?
What manual tests should be performed after the build, and by whom?
I perform manual tests with/without CBT to test the consistency.
I can perform manual tests after the build.
What's covered by the xcp-ng-tests test suite?
CBT tests in xcp-ng-tests are in development but they didn't catch this issue, so a new revision of the PR will handle this case.
What tests have been or will be added to CI for this change? If none, explain why.
Yes, this is a side project here:
https://project.vates.tech/vates-global/browse/XCPNG-672/
and
xcp-ng/xcp-ng-tests#541
but not yet upstream.
Xen Orchestra Impact
Does this affect existing features in Xen Orchestra, or add new features that could be useful?
Koji build (scratch, v8.3-incoming): https://koji.xcp-ng.org/taskinfo?taskID=111618